I have found in DOORS history objects that have the status: Read Locked Data. |
Re: Read Locked Data
|
Re: Read Locked Data SystemAdmin - Fri May 11 08:44:36 EDT 2012
And okay some things really happened like the discussed, but in my case when you compare one baseline more recent, with another older, theres a difference. I changed one attribute name, and the when saved a baseline, some values already answered have dissapeared. So after some time another baseline is created, and then the Read Locked Data appear. But the topic gave me some ideia of whats is happening,the question is, is it could be a DOORS problem? or is it a user who did something, kind of problem? |
Re: Read Locked Data Bruwbruw - Fri May 11 11:01:26 EDT 2012 You will see "Read Locked Data" in a column if you are indeed allowed to "R"ead the Object but not allowed to "R"ead that particular Attribute's values. The reasoning would be the same as that earlier post; that attribute no-longer exists and therefore you don't have "R"ead rights to it. I imagine however you are getting a delay in your denial of "R"ead rights. If you can see an attr-value in a baseline now, then rename the attribute in the current module, I think you will still be able to see the value in the baseline until you close the baseline and re-open it. Yes, this scheme is pretty clumsy but I wonder what elegant scheme they could implement instead. -Louie |